ci: fail when the architecture validator drifts from core - #97
Merged
Conversation
The validator here is a verbatim copy of the canonical file in exelearning/exelearning. Until now nothing enforced that: the copies stayed identical only because whoever changed one remembered to re-copy the rest. Twice during the recent review rounds that memory was the only safeguard, and once a sync commit was lost without anyone noticing for hours. The step fetches the canonical file from core's default branch and diffs it against this copy. A drift fails the job and prints the diff, so the report says what changed rather than just that something did. It needs no dependency and no setup: curl and diff are on the runner.
Contributor
Preview this PR in the Nextcloud Playground
A fresh Nextcloud boots in your browser with this branch's eXeLearning editor: |
The step was inserted ahead of `actions/checkout`, so the file it diffs did not exist yet and the job failed on its own first run. The check itself was right — the copy is byte-identical to core. What failed was where I put the step. The sibling repositories place it after their checkout already.
ignaciogros
approved these changes
Aug 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ci: fail when the architecture validator drifts from core
The validator here is a verbatim copy of the canonical file in
exelearning/exelearning. Until now nothing enforced that: the copies stayed
identical only because whoever changed one remembered to re-copy the rest.
Twice during the recent review rounds that memory was the only safeguard,
and once a sync commit was lost without anyone noticing for hours.
The step fetches the canonical file from core's default branch and diffs it
against this copy. A drift fails the job and prints the diff, so the report
says what changed rather than just that something did.
It needs no dependency and no setup: curl and diff are on the runner.
Verified locally: the step passes against the current copy, and fails with a readable diff when a line is appended to it.